Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 457946b2b85fd95c4023e0f3a8c5da96497cef9c25c9afd06c6f278b20ff8d7a

Tx prefix hash: b33ec3739693c46d79c20c5f6e581cbc7c9198addb01d6c660151d89e8e2bf9c
Tx public key: 54aa37cda1cf3b460369f53d251d3c727a159be83a3be21eb68f2a7911cb35e4
Timestamp: 1700765941 Timestamp [UCT]: 2023-11-23 18:59:01 Age [y:d:h:m:s]: 01:347:18:29:13
Block: 898093 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 507419 RingCT/type: yes/0
Extra: 0154aa37cda1cf3b460369f53d251d3c727a159be83a3be21eb68f2a7911cb35e402110000000475e3f0e9000000000000000000

1 output(s) for total of 0.649000544000 dcy

stealth address amount amount idx
00: ce1a087e556316614d7ed57def4ce01d0e4a97ce1c16b54c6786f9324d2e3d16 0.649000544000 1354496 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": 898103, "vin": [ { "gen": { "height": 898093 } } ], "vout": [ { "amount": 649000544, "target": { "key": "ce1a087e556316614d7ed57def4ce01d0e4a97ce1c16b54c6786f9324d2e3d16" } } ], "extra": [ 1, 84, 170, 55, 205, 161, 207, 59, 70, 3, 105, 245, 61, 37, 29, 60, 114, 122, 21, 155, 232, 58, 59, 226, 30, 182, 143, 42, 121, 17, 203, 53, 228, 2, 17, 0, 0, 0, 4, 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