Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1feb61a7fc5871e1e6533003e5bb37f1966d2b64c4f72b6f98d1cce87893df12

Tx prefix hash: 0c47f60ec0865470dca9e773db774f67a9ccc8b3b6eb09157b8a586c857f5d18
Tx public key: a256cd6af5e185ee9555f2d5c71088e881f348bfd06b09a367ef4d2e1ff540c9
Timestamp: 1719891571 Timestamp [UCT]: 2024-07-02 03:39:31 Age [y:d:h:m:s]: 00:273:07:26:44
Block: 1056646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195280 RingCT/type: yes/0
Extra: 01a256cd6af5e185ee9555f2d5c71088e881f348bfd06b09a367ef4d2e1ff540c90211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4780fe84462fd0bf46b85ce04ae160a15b1af53d3cb33af05a60886df48d2907 0.600000000000 1527063 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": 1056656, "vin": [ { "gen": { "height": 1056646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4780fe84462fd0bf46b85ce04ae160a15b1af53d3cb33af05a60886df48d2907" } } ], "extra": [ 1, 162, 86, 205, 106, 245, 225, 133, 238, 149, 85, 242, 213, 199, 16, 136, 232, 129, 243, 72, 191, 208, 107, 9, 163, 103, 239, 77, 46, 31, 245, 64, 201, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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