Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1fb61d911e4698fbdbfebcf22fedd86719dd428acdd2feee2068a319e3a0b82

Tx prefix hash: 89890f8df610683b2fc6e83154afd3d69fd6ad0fe611c8a4767296f038cdd151
Tx public key: 9498d12bcc2ba633205c9c0a7f7bd60662bc2229b1b3fa79b8fb72fda6de8487
Timestamp: 1711697452 Timestamp [UCT]: 2024-03-29 07:30:52 Age [y:d:h:m:s]: 01:229:09:31:24
Block: 988736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 422626 RingCT/type: yes/0
Extra: 019498d12bcc2ba633205c9c0a7f7bd60662bc2229b1b3fa79b8fb72fda6de84870211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2eedef758b42e04472c364c3c4b72792b6756a2323c752ab98d0f1aaf6aea665 0.600000000000 1449017 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": 988746, "vin": [ { "gen": { "height": 988736 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2eedef758b42e04472c364c3c4b72792b6756a2323c752ab98d0f1aaf6aea665" } } ], "extra": [ 1, 148, 152, 209, 43, 204, 43, 166, 51, 32, 92, 156, 10, 127, 123, 214, 6, 98, 188, 34, 41, 177, 179, 250, 121, 184, 251, 114, 253, 166, 222, 132, 135, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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