Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d7db893f9e45596ec48fdd0a14bdb66d4e6edcde50b018f981ac0b5b22a0f2d

Tx prefix hash: 4267c90a6c3380ec7fab3b6e29794049b517162b54305c809bb73e62fd55caa0
Tx public key: f10f54ace2efc8005ed421839a03a47a589eac430bcf9834a2c7925c886e3924
Timestamp: 1702128489 Timestamp [UCT]: 2023-12-09 13:28:09 Age [y:d:h:m:s]: 01:156:03:35:05
Block: 909384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372777 RingCT/type: yes/0
Extra: 01f10f54ace2efc8005ed421839a03a47a589eac430bcf9834a2c7925c886e392402110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e359941e41921b3d44f7d08a47c67307f692dbd679b92688851e3c063f995cd0 0.600000000000 1366469 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": 909394, "vin": [ { "gen": { "height": 909384 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e359941e41921b3d44f7d08a47c67307f692dbd679b92688851e3c063f995cd0" } } ], "extra": [ 1, 241, 15, 84, 172, 226, 239, 200, 0, 94, 212, 33, 131, 154, 3, 164, 122, 88, 158, 172, 67, 11, 207, 152, 52, 162, 199, 146, 92, 136, 110, 57, 36, 2, 17, 0, 0, 0, 2, 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