Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a24ff78899c8f1ee67b0b4e881f57efeb597b2898ee8fbe2460d61fefc9c7253

Tx prefix hash: 47424b02847acb801066b112784ef0dbfc3f832c2a9f1f32017c06d47d8bcf93
Tx public key: b5902d734dedf3bbe6bd748a5a113a65828d0a4da118cd56ace79aa697e7fa8b
Timestamp: 1578945588 Timestamp [UCT]: 2020-01-13 19:59:48 Age [y:d:h:m:s]: 04:297:09:36:21
Block: 44933 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1101945 RingCT/type: yes/0
Extra: 01b5902d734dedf3bbe6bd748a5a113a65828d0a4da118cd56ace79aa697e7fa8b021100000001d81c26c0000000000000000000

1 output(s) for total of 435.631382930000 dcy

stealth address amount amount idx
00: ad4b1e1de8199dd5aa849468618af9c8405fd69a155820425c37cf727ccb7f1d 435.631382930000 81937 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": 44943, "vin": [ { "gen": { "height": 44933 } } ], "vout": [ { "amount": 435631382930, "target": { "key": "ad4b1e1de8199dd5aa849468618af9c8405fd69a155820425c37cf727ccb7f1d" } } ], "extra": [ 1, 181, 144, 45, 115, 77, 237, 243, 187, 230, 189, 116, 138, 90, 17, 58, 101, 130, 141, 10, 77, 161, 24, 205, 86, 172, 231, 154, 166, 151, 231, 250, 139, 2, 17, 0, 0, 0, 1, 216, 28, 38, 192, 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