Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abdfb38c6fe1b21e16b7a324374746f3c18dfda1aa7282400213de1b34c0784c

Tx prefix hash: 515fe1d4acc987fa4e757f53b686b24fa6663a6dcb221f6319be2a5b462cf24e
Tx public key: f241b8f5c2d4115108dbff41736b142ba671fafed4073f6540cca38c0e534b99
Timestamp: 1719541975 Timestamp [UCT]: 2024-06-28 02:32:55 Age [y:d:h:m:s]: 00:306:07:47:52
Block: 1053754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218931 RingCT/type: yes/0
Extra: 01f241b8f5c2d4115108dbff41736b142ba671fafed4073f6540cca38c0e534b9902110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44b500ea62c8a84156e33e7d9f1b97eab795fc580cd5f8ed87bc19c0c2863a2c 0.600000000000 1524103 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": 1053764, "vin": [ { "gen": { "height": 1053754 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44b500ea62c8a84156e33e7d9f1b97eab795fc580cd5f8ed87bc19c0c2863a2c" } } ], "extra": [ 1, 242, 65, 184, 245, 194, 212, 17, 81, 8, 219, 255, 65, 115, 107, 20, 43, 166, 113, 250, 254, 212, 7, 63, 101, 64, 204, 163, 140, 14, 83, 75, 153, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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