Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf050a75b34a9f70e668564ad2ca5b1b39a26f34176325f35dff77051bc10b1d

Tx prefix hash: 2c95870dbf88a20243e2057d8e9915fb572fc36becb6160f061d64a43a1bfee6
Tx public key: f8f154719cc3d784c4df1cc5c8c0ac40a845c94464fdcf2c64a35bbd692c150e
Timestamp: 1736658349 Timestamp [UCT]: 2025-01-12 05:05:49 Age [y:d:h:m:s]: 00:339:19:37:32
Block: 1195515 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240422 RingCT/type: yes/0
Extra: 01f8f154719cc3d784c4df1cc5c8c0ac40a845c94464fdcf2c64a35bbd692c150e0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 99a36d31ed0b0154ebf2137202402ab2af50843f4eb5e9696f8aa0a3e3fec004 0.600000000000 1682106 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": 1195525, "vin": [ { "gen": { "height": 1195515 } } ], "vout": [ { "amount": 600000000, "target": { "key": "99a36d31ed0b0154ebf2137202402ab2af50843f4eb5e9696f8aa0a3e3fec004" } } ], "extra": [ 1, 248, 241, 84, 113, 156, 195, 215, 132, 196, 223, 28, 197, 200, 192, 172, 64, 168, 69, 201, 68, 100, 253, 207, 44, 100, 163, 91, 189, 105, 44, 21, 14, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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