Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f019fb88dfae01abbc3cf1bfe356eb4a53c5b291f4f8dcd64b535e9f87c592c

Tx prefix hash: e71420afee7ecb7a81aab8876c812718e3a099237c26cf40991cdbb0b19b9c23
Tx public key: 1fea5ce568551780a3490ebd6282160347d0c1741e79808691f46d5ee4e2d505
Timestamp: 1721771460 Timestamp [UCT]: 2024-07-23 21:51:00 Age [y:d:h:m:s]: 00:248:16:32:20
Block: 1072235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177649 RingCT/type: yes/0
Extra: 011fea5ce568551780a3490ebd6282160347d0c1741e79808691f46d5ee4e2d505021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c7f6b62314bfcf1e930383f21d7ec5b45c9e5831570bf4e552a923324d8e3fa 0.600000000000 1544692 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": 1072245, "vin": [ { "gen": { "height": 1072235 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c7f6b62314bfcf1e930383f21d7ec5b45c9e5831570bf4e552a923324d8e3fa" } } ], "extra": [ 1, 31, 234, 92, 229, 104, 85, 23, 128, 163, 73, 14, 189, 98, 130, 22, 3, 71, 208, 193, 116, 30, 121, 128, 134, 145, 244, 109, 94, 228, 226, 213, 5, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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