Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49ed009f99b5a3dd6e782dc075924c930ef1eae1e0172e5cee9d6629b5a4a518

Tx prefix hash: 8c7db015ff353302c7471e2a3a1c7746dbcb1f4beae9f303d32018f19d3b1e5d
Tx public key: f8336ef0a77c7a5d5a293644b2874867661c0b69d84ee43cf7cb11dba325f97e
Timestamp: 1646827112 Timestamp [UCT]: 2022-03-09 11:58:32 Age [y:d:h:m:s]: 03:236:19:52:04
Block: 454667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 947123 RingCT/type: yes/0
Extra: 01f8336ef0a77c7a5d5a293644b2874867661c0b69d84ee43cf7cb11dba325f97e021100000004a8c141c5000000000000000000

1 output(s) for total of 19.120522666000 dcy

stealth address amount amount idx
00: f4abe49373ef1f5a4e666cecfab7313864cb1f01461834dab125103d9939ca12 19.120522666000 870354 of 0

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": 454677, "vin": [ { "gen": { "height": 454667 } } ], "vout": [ { "amount": 19120522666, "target": { "key": "f4abe49373ef1f5a4e666cecfab7313864cb1f01461834dab125103d9939ca12" } } ], "extra": [ 1, 248, 51, 110, 240, 167, 124, 122, 93, 90, 41, 54, 68, 178, 135, 72, 103, 102, 28, 11, 105, 216, 78, 228, 60, 247, 203, 17, 219, 163, 37, 249, 126, 2, 17, 0, 0, 0, 4, 168, 193, 65, 197, 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