Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b4f8b11d13ed7627772066d5718e8c03da87067c06610b38bb5f3db4c0735de

Tx prefix hash: 7d64e47afe4ddb7acc6c8c589c9c6f7cdf2987c218deea1597d783b8a5f173f3
Tx public key: 225e09df81facd580a394b79c8d949e94d22c823bfe3bf03d59392ab69a29a5d
Timestamp: 1705586215 Timestamp [UCT]: 2024-01-18 13:56:55 Age [y:d:h:m:s]: 01:146:15:33:15
Block: 938043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365897 RingCT/type: yes/0
Extra: 01225e09df81facd580a394b79c8d949e94d22c823bfe3bf03d59392ab69a29a5d02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52c943d36e3f6fea273570d305da81ab17a8151ec0093298c61f423387b1e2d7 0.600000000000 1396107 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": 938053, "vin": [ { "gen": { "height": 938043 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52c943d36e3f6fea273570d305da81ab17a8151ec0093298c61f423387b1e2d7" } } ], "extra": [ 1, 34, 94, 9, 223, 129, 250, 205, 88, 10, 57, 75, 121, 200, 217, 73, 233, 77, 34, 200, 35, 191, 227, 191, 3, 213, 147, 146, 171, 105, 162, 154, 93, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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