Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 639d8b028cb084736bcc2e0eb9889b5289790cbcae571f3552c60883f2a61c98

Tx prefix hash: 4c174d2b471a75073695903e9cc2c64df89829e9fbb03124eeb9561b28b72750
Tx public key: f15f4302997525bc8ffd81a2d70b4a5255ddda7e93cbab3c995cdad7dd17b0f7
Timestamp: 1719559129 Timestamp [UCT]: 2024-06-28 07:18:49 Age [y:d:h:m:s]: 00:351:09:27:24
Block: 1053898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251062 RingCT/type: yes/0
Extra: 01f15f4302997525bc8ffd81a2d70b4a5255ddda7e93cbab3c995cdad7dd17b0f70211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3668eb5d6e8c8e5970f5d847aef7b1d2357d1205a8fc8045db4857f03f52ad94 0.600000000000 1524251 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1053908, "vin": [ { "gen": { "height": 1053898 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3668eb5d6e8c8e5970f5d847aef7b1d2357d1205a8fc8045db4857f03f52ad94" } } ], "extra": [ 1, 241, 95, 67, 2, 153, 117, 37, 188, 143, 253, 129, 162, 215, 11, 74, 82, 85, 221, 218, 126, 147, 203, 171, 60, 153, 92, 218, 215, 221, 23, 176, 247, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8