Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd4e2ccc8e1ddd1737fa530c7befab08f3fe8bec9fd47e6ea9eb9c99191aa761

Tx prefix hash: dcad5719d59d6e61e4a4e2ac6921ca983f75ae87085650a71ef8134468001155
Tx public key: b82422e9976b00b5a06c4333709b6eec288a03419b41de6b4c000b4d19751070
Timestamp: 1731882158 Timestamp [UCT]: 2024-11-17 22:22:38 Age [y:d:h:m:s]: 00:005:23:09:59
Block: 1155979 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4256 RingCT/type: yes/0
Extra: 01b82422e9976b00b5a06c4333709b6eec288a03419b41de6b4c000b4d19751070021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b44dba03152a67e1ae2317fbd1b75a68d8b4c1d091337fc9a158d4a13c0a8cbf 0.600000000000 1641598 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": 1155989, "vin": [ { "gen": { "height": 1155979 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b44dba03152a67e1ae2317fbd1b75a68d8b4c1d091337fc9a158d4a13c0a8cbf" } } ], "extra": [ 1, 184, 36, 34, 233, 151, 107, 0, 181, 160, 108, 67, 51, 112, 155, 110, 236, 40, 138, 3, 65, 155, 65, 222, 107, 76, 0, 11, 77, 25, 117, 16, 112, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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