Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b7de2c01f203b60c11c70ac502c9a3bd6f766886ed064e9f6054fb885b8a055

Tx prefix hash: 8c805d382a0396e7617f0fe9055569c4be44af8c14d14e88677fdbd1fdc3e6c2
Tx public key: de842022a07dfa5debc5da797b91f80841bff10ecbb60ee8d416e9e26e8fa954
Timestamp: 1755828069 Timestamp [UCT]: 2025-08-22 02:01:09 Age [y:d:h:m:s]: 00:091:20:29:52
Block: 1351662 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65590 RingCT/type: yes/0
Extra: 01de842022a07dfa5debc5da797b91f80841bff10ecbb60ee8d416e9e26e8fa95402110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a1a489f229113535d42f043d86c2a2d0d7121728bce1350842ad2dc7bc1a7ff 0.600000000000 1839619 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": 1351672, "vin": [ { "gen": { "height": 1351662 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a1a489f229113535d42f043d86c2a2d0d7121728bce1350842ad2dc7bc1a7ff" } } ], "extra": [ 1, 222, 132, 32, 34, 160, 125, 250, 93, 235, 197, 218, 121, 123, 145, 248, 8, 65, 191, 241, 14, 203, 182, 14, 232, 212, 22, 233, 226, 110, 143, 169, 84, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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