Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5b9927013e19e02763d019527904d550d4bad9f1845846fdc791a252bb926b3

Tx prefix hash: e93551a1899959ec21ca11b175dc6f414cadb3f024cc49740745e19fbedbc205
Tx public key: 062138aa2440cd6c59a2d57f747c7d86b058d2337f35964d53a3ff5d7b95b280
Timestamp: 1706902475 Timestamp [UCT]: 2024-02-02 19:34:35 Age [y:d:h:m:s]: 00:341:09:42:30
Block: 948952 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244428 RingCT/type: yes/0
Extra: 01062138aa2440cd6c59a2d57f747c7d86b058d2337f35964d53a3ff5d7b95b2800211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2e4fa826953d1f59fcedb33eba5c3b1ad68c2647d0cb9e8f2c05a6584add846 0.600000000000 1407472 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": 948962, "vin": [ { "gen": { "height": 948952 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2e4fa826953d1f59fcedb33eba5c3b1ad68c2647d0cb9e8f2c05a6584add846" } } ], "extra": [ 1, 6, 33, 56, 170, 36, 64, 205, 108, 89, 162, 213, 127, 116, 124, 125, 134, 176, 88, 210, 51, 127, 53, 150, 77, 83, 163, 255, 93, 123, 149, 178, 128, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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