Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fcaeeb4100c74d6843b8baadce0822502198ae61b09e8a0d8786a64f903ffbc

Tx prefix hash: 1fbdb37da12eb9a2d645738c221bcb5895af05e49137ec07211d482f20fd5fc6
Tx public key: 147fd41ef88ff8fd7cd5cb651a5e36f7d9b3588daf3c87ec71845e0191c8fbb3
Timestamp: 1705483264 Timestamp [UCT]: 2024-01-17 09:21:04 Age [y:d:h:m:s]: 01:151:00:26:36
Block: 937189 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368971 RingCT/type: yes/0
Extra: 01147fd41ef88ff8fd7cd5cb651a5e36f7d9b3588daf3c87ec71845e0191c8fbb30211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f38ffe588791bc7bfc524541966b07fb7ae4ff6085ecdc1bc3b568542c8734d0 0.600000000000 1395233 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": 937199, "vin": [ { "gen": { "height": 937189 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f38ffe588791bc7bfc524541966b07fb7ae4ff6085ecdc1bc3b568542c8734d0" } } ], "extra": [ 1, 20, 127, 212, 30, 248, 143, 248, 253, 124, 213, 203, 101, 26, 94, 54, 247, 217, 179, 88, 141, 175, 60, 135, 236, 113, 132, 94, 1, 145, 200, 251, 179, 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