Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dca6be69486c8d0ae474d076628c7d820485ec610ba400e60cf20b99c0aef453

Tx prefix hash: ab38f5e65bf71a6db6c70d15f2c4508b0595c949fef4c3d058ddcccb61bea2c0
Tx public key: 47434af3ad938bd507d3a4af489f36b6de33eddd5d5332b19aa4ebc10dda44d5
Timestamp: 1707133141 Timestamp [UCT]: 2024-02-05 11:39:01 Age [y:d:h:m:s]: 01:123:20:52:15
Block: 950870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349639 RingCT/type: yes/0
Extra: 0147434af3ad938bd507d3a4af489f36b6de33eddd5d5332b19aa4ebc10dda44d50211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5cd82a1b213321ce7d0f74f34936b71b0e0b762b964f6ca444c74401aaffd7e6 0.600000000000 1409556 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": 950880, "vin": [ { "gen": { "height": 950870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5cd82a1b213321ce7d0f74f34936b71b0e0b762b964f6ca444c74401aaffd7e6" } } ], "extra": [ 1, 71, 67, 74, 243, 173, 147, 139, 213, 7, 211, 164, 175, 72, 159, 54, 182, 222, 51, 237, 221, 93, 83, 50, 177, 154, 164, 235, 193, 13, 218, 68, 213, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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