Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 675fa56ce5d9c0bb2cae6db4e06ef6dfd9e56cc1de1ff7ecb147e1c34ccdef80

Tx prefix hash: 2b2d2044dfa14911b2865e9bfd014bc924526c2efc46364be334f641640a3134
Tx public key: b37c93bedc36bb15afc9b67e95d3798a1e10a087d4c56c2795b33c9095de7935
Timestamp: 1711411366 Timestamp [UCT]: 2024-03-26 00:02:46 Age [y:d:h:m:s]: 01:238:22:38:01
Block: 986378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 429449 RingCT/type: yes/0
Extra: 01b37c93bedc36bb15afc9b67e95d3798a1e10a087d4c56c2795b33c9095de793502110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 169956b1d6f218bc1efe664ffcd0fdd262abda6abc239eb229c74df2294adb71 0.600000000000 1446607 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": 986388, "vin": [ { "gen": { "height": 986378 } } ], "vout": [ { "amount": 600000000, "target": { "key": "169956b1d6f218bc1efe664ffcd0fdd262abda6abc239eb229c74df2294adb71" } } ], "extra": [ 1, 179, 124, 147, 190, 220, 54, 187, 21, 175, 201, 182, 126, 149, 211, 121, 138, 30, 16, 160, 135, 212, 197, 108, 39, 149, 179, 60, 144, 149, 222, 121, 53, 2, 17, 0, 0, 0, 6, 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