Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a03315753c664da9e1a7205d7a42e9a333f017b7ce552d2f79ca3147054fa6d2

Tx prefix hash: c28684f1c44546b654c8eee71621dc15d76647fed6a657fb7c834469b841dbb4
Tx public key: 9ae8284ed0203148130cefe7f84286cc7a7d76eee4e0f4a38f0aae02c29622ed
Timestamp: 1694276577 Timestamp [UCT]: 2023-09-09 16:22:57 Age [y:d:h:m:s]: 01:280:10:30:34
Block: 844481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 461488 RingCT/type: yes/0
Extra: 019ae8284ed0203148130cefe7f84286cc7a7d76eee4e0f4a38f0aae02c29622ed02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.976976126000 dcy

stealth address amount amount idx
00: 8967f8b24ef5a3c97b9de37a18cc86e45ad26a832e4c0a68a62d00c924b8189f 0.976976126000 1297793 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": 844491, "vin": [ { "gen": { "height": 844481 } } ], "vout": [ { "amount": 976976126, "target": { "key": "8967f8b24ef5a3c97b9de37a18cc86e45ad26a832e4c0a68a62d00c924b8189f" } } ], "extra": [ 1, 154, 232, 40, 78, 208, 32, 49, 72, 19, 12, 239, 231, 248, 66, 134, 204, 122, 125, 118, 238, 228, 224, 244, 163, 143, 10, 174, 2, 194, 150, 34, 237, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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