Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 518f7de41bfd37d27774fd7acafb99fd6c783dd4439d90ee4605bd31ca91a6dd

Tx prefix hash: ef3b5a02af691d569f1ae31fd7863a14e7b96b3000788bdcbe79e6c95bb40f3c
Tx public key: 2d17e5213efe73af5da3f08cecd88a3fd51b74e40d0cbc043e2da6ece61bda34
Timestamp: 1749451268 Timestamp [UCT]: 2025-06-09 06:41:08 Age [y:d:h:m:s]: 00:157:05:43:42
Block: 1301171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110055 RingCT/type: yes/0
Extra: 012d17e5213efe73af5da3f08cecd88a3fd51b74e40d0cbc043e2da6ece61bda3402110000000343846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03fe053286f1ee3d2db84e034013fed20a130fd1275f9a2e94e3a84587421f46 0.600000000000 1788724 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": 1301181, "vin": [ { "gen": { "height": 1301171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03fe053286f1ee3d2db84e034013fed20a130fd1275f9a2e94e3a84587421f46" } } ], "extra": [ 1, 45, 23, 229, 33, 62, 254, 115, 175, 93, 163, 240, 140, 236, 216, 138, 63, 213, 27, 116, 228, 13, 12, 188, 4, 62, 45, 166, 236, 230, 27, 218, 52, 2, 17, 0, 0, 0, 3, 67, 132, 109, 102, 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