Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ca11e94c1c5cb3f0dd95d9da61d53c45fe9f07530b6872bac3ed6a49aa9577a

Tx prefix hash: e4f395b8b20d58a7bde893315acd0a9a522f2ee61a1228c030ee72a2d6f06f1f
Tx public key: d5c769666cdac793543e1b76ab8b09b57a8fba56ab788123ad708f7eb731047a
Timestamp: 1700914122 Timestamp [UCT]: 2023-11-25 12:08:42 Age [y:d:h:m:s]: 01:150:10:13:51
Block: 899330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368669 RingCT/type: yes/0
Extra: 01d5c769666cdac793543e1b76ab8b09b57a8fba56ab788123ad708f7eb731047a02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.642904351000 dcy

stealth address amount amount idx
00: e63911bf0f6978eea014cdb7ec549d5eb6923cc30ddeec4bf2101609e72ead91 0.642904351000 1355779 of 0

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": 899340, "vin": [ { "gen": { "height": 899330 } } ], "vout": [ { "amount": 642904351, "target": { "key": "e63911bf0f6978eea014cdb7ec549d5eb6923cc30ddeec4bf2101609e72ead91" } } ], "extra": [ 1, 213, 199, 105, 102, 108, 218, 199, 147, 84, 62, 27, 118, 171, 139, 9, 181, 122, 143, 186, 86, 171, 120, 129, 35, 173, 112, 143, 126, 183, 49, 4, 122, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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