Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: feebff2440f0ca9c2c18ba149cfc4afd08114eb497e4fe5e5138ee5cb99ac427

Tx prefix hash: 69e5645788c465de86d49a5a13f1ca2db21fd86d50eb66199028afd818e945cc
Tx public key: 0e8ae41330206ba6c46201779797bfd9828d16fa976936ed416a72b88c76d08c
Timestamp: 1696526452 Timestamp [UCT]: 2023-10-05 17:20:52 Age [y:d:h:m:s]: 02:041:03:57:33
Block: 863143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 549066 RingCT/type: yes/0
Extra: 010e8ae41330206ba6c46201779797bfd9828d16fa976936ed416a72b88c76d08c02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.847322952000 dcy

stealth address amount amount idx
00: 3de99c55225f595b5c2e0b12b3ddc5aaded0df465c32207ef1de8b90d7f6d171 0.847322952000 1317591 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": 863153, "vin": [ { "gen": { "height": 863143 } } ], "vout": [ { "amount": 847322952, "target": { "key": "3de99c55225f595b5c2e0b12b3ddc5aaded0df465c32207ef1de8b90d7f6d171" } } ], "extra": [ 1, 14, 138, 228, 19, 48, 32, 107, 166, 196, 98, 1, 119, 151, 151, 191, 217, 130, 141, 22, 250, 151, 105, 54, 237, 65, 106, 114, 184, 140, 118, 208, 140, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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