Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5854673ad211c744f359afd4e4207d8c6e0ed298a992dc54ec3665f34a7c80c4

Tx prefix hash: 53f7d6e09827abb4f071b988be97d309a36118875b1bafea22d521b32e82d410
Tx public key: 2a5439dc2fafd8089b897dfb9faed8ba0ac24498ba3ac71938e600a2fff11ab1
Timestamp: 1748144510 Timestamp [UCT]: 2025-05-25 03:41:50 Age [y:d:h:m:s]: 00:178:16:31:26
Block: 1290352 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125400 RingCT/type: yes/0
Extra: 012a5439dc2fafd8089b897dfb9faed8ba0ac24498ba3ac71938e600a2fff11ab10211000000021f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efb81e6ff27e74aaeebe159fb2e4616a305de514ea922ed4d57e51c13d12dea0 0.600000000000 1777821 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": 1290362, "vin": [ { "gen": { "height": 1290352 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efb81e6ff27e74aaeebe159fb2e4616a305de514ea922ed4d57e51c13d12dea0" } } ], "extra": [ 1, 42, 84, 57, 220, 47, 175, 216, 8, 155, 137, 125, 251, 159, 174, 216, 186, 10, 194, 68, 152, 186, 58, 199, 25, 56, 230, 0, 162, 255, 241, 26, 177, 2, 17, 0, 0, 0, 2, 31, 144, 81, 122, 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