Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb660798a2a47911921327aa81077c889b86f1d9b84ef4ed4f6a4222e9c2a758

Tx prefix hash: 380ae98361d6a9c3ecfe72202f377ef403f4f8582947aaac45c5a0ab03c459ae
Tx public key: ab5492c4fad0da9c1214ff6ee682f256c5cb680530b8c824be571f3730c01c00
Timestamp: 1718824259 Timestamp [UCT]: 2024-06-19 19:10:59 Age [y:d:h:m:s]: 00:157:08:35:41
Block: 1047805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112624 RingCT/type: yes/0
Extra: 01ab5492c4fad0da9c1214ff6ee682f256c5cb680530b8c824be571f3730c01c000211000000020bba16d7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4965bc442920aa880a573196d4e3bc390dcefc9eacd3dbe80239867dbb4d2aa8 0.600000000000 1517724 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": 1047815, "vin": [ { "gen": { "height": 1047805 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4965bc442920aa880a573196d4e3bc390dcefc9eacd3dbe80239867dbb4d2aa8" } } ], "extra": [ 1, 171, 84, 146, 196, 250, 208, 218, 156, 18, 20, 255, 110, 230, 130, 242, 86, 197, 203, 104, 5, 48, 184, 200, 36, 190, 87, 31, 55, 48, 192, 28, 0, 2, 17, 0, 0, 0, 2, 11, 186, 22, 215, 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