Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a76b37fb4110f6c3ee4cf7e3a2a93dcff8c4fd6048f51f45c63a347d604742d

Tx prefix hash: 465ba2fe1eada6d2485e64f375441cca0560d1ca3594ef614f55229b2be0ad0d
Tx public key: 80329335378c6c457aa26c14329f9e2dae4f2fce861fe96e9207dabbd9c586ac
Timestamp: 1729762400 Timestamp [UCT]: 2024-10-24 09:33:20 Age [y:d:h:m:s]: 00:192:07:25:46
Block: 1138454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137260 RingCT/type: yes/0
Extra: 0180329335378c6c457aa26c14329f9e2dae4f2fce861fe96e9207dabbd9c586ac0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 368e711970a0c1a2219a20df60ce4a4b93f39ddb5c1828550e223c1c41958861 0.600000000000 1622129 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": 1138464, "vin": [ { "gen": { "height": 1138454 } } ], "vout": [ { "amount": 600000000, "target": { "key": "368e711970a0c1a2219a20df60ce4a4b93f39ddb5c1828550e223c1c41958861" } } ], "extra": [ 1, 128, 50, 147, 53, 55, 140, 108, 69, 122, 162, 108, 20, 50, 159, 158, 45, 174, 79, 47, 206, 134, 31, 233, 110, 146, 7, 218, 187, 217, 197, 134, 172, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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