Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a12bd818ce6c04bf5fe32f7ac1faf263e2dffe427576bd2507db9f936c03f3cc

Tx prefix hash: a48cbe61dc27ce48f5c8aa4a7287ac9064d3010174d10c3e79041373b0b16b14
Tx public key: 25b9350c473f36904c4f101eaf400628ed1982a1f2fa330b5d7fc3b81808407e
Timestamp: 1713359373 Timestamp [UCT]: 2024-04-17 13:09:33 Age [y:d:h:m:s]: 01:032:11:30:43
Block: 1002498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284187 RingCT/type: yes/0
Extra: 0125b9350c473f36904c4f101eaf400628ed1982a1f2fa330b5d7fc3b81808407e0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8795e1e8ccd6bae00ed9bad0b961839b186234b162ae959441fd99c4a4d1abe0 0.600000000000 1463014 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": 1002508, "vin": [ { "gen": { "height": 1002498 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8795e1e8ccd6bae00ed9bad0b961839b186234b162ae959441fd99c4a4d1abe0" } } ], "extra": [ 1, 37, 185, 53, 12, 71, 63, 54, 144, 76, 79, 16, 30, 175, 64, 6, 40, 237, 25, 130, 161, 242, 250, 51, 11, 93, 127, 195, 184, 24, 8, 64, 126, 2, 17, 0, 0, 0, 2, 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