Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0448c92d96491c8e3b28b35ff3036185a2be241c8c3e5694a428a6680c839b80

Tx prefix hash: 40d5d75e8bcc8aca7b88c01fbce733f9c2552e1dc24b4e47718ec1cb5e92ff58
Tx public key: ab86907b9d43da9fa409567242034839bd31821ef2cf2c3bb4068c999e2f7bc9
Timestamp: 1717253586 Timestamp [UCT]: 2024-06-01 14:53:06 Age [y:d:h:m:s]: 00:308:11:38:52
Block: 1034790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220461 RingCT/type: yes/0
Extra: 01ab86907b9d43da9fa409567242034839bd31821ef2cf2c3bb4068c999e2f7bc9021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf5b03ec7a47ad9aaea7df9bb18d5add5f4e21f84104cd6c80557ebf45103d22 0.600000000000 1503309 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": 1034800, "vin": [ { "gen": { "height": 1034790 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf5b03ec7a47ad9aaea7df9bb18d5add5f4e21f84104cd6c80557ebf45103d22" } } ], "extra": [ 1, 171, 134, 144, 123, 157, 67, 218, 159, 164, 9, 86, 114, 66, 3, 72, 57, 189, 49, 130, 30, 242, 207, 44, 59, 180, 6, 140, 153, 158, 47, 123, 201, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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