Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de0c19356d940a0bf831a18cd1056ed197117154e61118999d12de42f8a28924

Tx prefix hash: f0e8a08e9eee193b5df05a8ada761278332d44b99858adaa1d5238a2070142a7
Tx public key: 6595af309df1e2a3dd86cf3a5631b104c67240cee3db18a3180b8e21b0477b75
Timestamp: 1734227572 Timestamp [UCT]: 2024-12-15 01:52:52 Age [y:d:h:m:s]: 00:094:21:34:18
Block: 1175420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67612 RingCT/type: yes/0
Extra: 016595af309df1e2a3dd86cf3a5631b104c67240cee3db18a3180b8e21b0477b75021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c7e8c4e8819d1ae8e037131f2206fa0c381b26706919c2d04db8b1dd0bf41d0 0.600000000000 1661697 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": 1175430, "vin": [ { "gen": { "height": 1175420 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c7e8c4e8819d1ae8e037131f2206fa0c381b26706919c2d04db8b1dd0bf41d0" } } ], "extra": [ 1, 101, 149, 175, 48, 157, 241, 226, 163, 221, 134, 207, 58, 86, 49, 177, 4, 198, 114, 64, 206, 227, 219, 24, 163, 24, 11, 142, 33, 176, 71, 123, 117, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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