Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5d5c0d387c8f08ef4a87d27a164a68a9691fd2db627dece16c3bb01cf2e3a22

Tx prefix hash: afa8ffa53916a4d0f7db6fe3f5aca75d0dc86387944598434091346774280a5a
Tx public key: 2f9b46daf18c20f25a85ca8fb53c6d77edae5bc5349cf710ba6e8c3eca2491c1
Timestamp: 1657257553 Timestamp [UCT]: 2022-07-08 05:19:13 Age [y:d:h:m:s]: 02:256:10:30:03
Block: 539100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 704419 RingCT/type: yes/0
Extra: 012f9b46daf18c20f25a85ca8fb53c6d77edae5bc5349cf710ba6e8c3eca2491c1021100000010bf7ee4e7000000000000000000

1 output(s) for total of 10.040100434000 dcy

stealth address amount amount idx
00: daabdb37b72b66c3856e5bb18fbffc2b4e55c6c0fd91392c888cb08012a59e0d 10.040100434000 969171 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": 539110, "vin": [ { "gen": { "height": 539100 } } ], "vout": [ { "amount": 10040100434, "target": { "key": "daabdb37b72b66c3856e5bb18fbffc2b4e55c6c0fd91392c888cb08012a59e0d" } } ], "extra": [ 1, 47, 155, 70, 218, 241, 140, 32, 242, 90, 133, 202, 143, 181, 60, 109, 119, 237, 174, 91, 197, 52, 156, 247, 16, 186, 110, 140, 62, 202, 36, 145, 193, 2, 17, 0, 0, 0, 16, 191, 126, 228, 231, 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