Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 859b46ba4c2e49dee1b13d87b45a669b08cb37fdaec5b41cc8db2e377dcbaee3

Tx prefix hash: 0182b784ac69fd3804a9554bd41a00c41fb67857b33ed7fb643cbe848dd8bcc1
Tx public key: 693f264de9f3a35dc206dd51f4372a8462e8c43c8290c305a85e24151ce717c2
Timestamp: 1744087656 Timestamp [UCT]: 2025-04-08 04:47:36 Age [y:d:h:m:s]: 00:036:13:51:54
Block: 1256739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26192 RingCT/type: yes/0
Extra: 01693f264de9f3a35dc206dd51f4372a8462e8c43c8290c305a85e24151ce717c2021100000003dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd523f85ea392b71042a33340d9dfd648a67e1e35db0ff8f4e077828459e73bf 0.600000000000 1743856 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": 1256749, "vin": [ { "gen": { "height": 1256739 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd523f85ea392b71042a33340d9dfd648a67e1e35db0ff8f4e077828459e73bf" } } ], "extra": [ 1, 105, 63, 38, 77, 233, 243, 163, 93, 194, 6, 221, 81, 244, 55, 42, 132, 98, 232, 196, 60, 130, 144, 195, 5, 168, 94, 36, 21, 28, 231, 23, 194, 2, 17, 0, 0, 0, 3, 219, 181, 113, 193, 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