Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4697c3d4b729e07163514d2e5d8bca3151a63082ba552e89a123767dbe257f48

Tx prefix hash: 8b6dc5af7d18bfc5400c902868865d99e0591f286f05a6f8910a0b968c57bf39
Tx public key: 59df58a3bd27238ec207b17da10dede64a9c271c1fec7fca422b202ddab621ea
Timestamp: 1710728894 Timestamp [UCT]: 2024-03-18 02:28:14 Age [y:d:h:m:s]: 00:309:11:38:57
Block: 980715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221467 RingCT/type: yes/0
Extra: 0159df58a3bd27238ec207b17da10dede64a9c271c1fec7fca422b202ddab621ea02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d2fff178ef2682fa95fe20ef9bf8d29314f1656a4834e4be882082304fb2739 0.600000000000 1440796 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": 980725, "vin": [ { "gen": { "height": 980715 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d2fff178ef2682fa95fe20ef9bf8d29314f1656a4834e4be882082304fb2739" } } ], "extra": [ 1, 89, 223, 88, 163, 189, 39, 35, 142, 194, 7, 177, 125, 161, 13, 237, 230, 74, 156, 39, 28, 31, 236, 127, 202, 66, 43, 32, 45, 218, 182, 33, 234, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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