Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf98a37672a166a239bc51785c3a744dbfbe4899c8c7a8f854a6b46786d8d32e

Tx prefix hash: 2e4c4b20cf9393fbf4ce1d06eb83e3b78b578f98835fe11b0a2d2371a8d0b3f5
Tx public key: c43bb5c24eb912856883a5647b785e01274590e911673a1270d4dd16cd0713aa
Timestamp: 1731053116 Timestamp [UCT]: 2024-11-08 08:05:16 Age [y:d:h:m:s]: 01:000:22:46:53
Block: 1149113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259084 RingCT/type: yes/0
Extra: 01c43bb5c24eb912856883a5647b785e01274590e911673a1270d4dd16cd0713aa0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1079348f9b6383a8c5323d3b0a8da2d3fd95d69e769f599f338ec78c1960a123 0.600000000000 1634118 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": 1149123, "vin": [ { "gen": { "height": 1149113 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1079348f9b6383a8c5323d3b0a8da2d3fd95d69e769f599f338ec78c1960a123" } } ], "extra": [ 1, 196, 59, 181, 194, 78, 185, 18, 133, 104, 131, 165, 100, 123, 120, 94, 1, 39, 69, 144, 233, 17, 103, 58, 18, 112, 212, 221, 22, 205, 7, 19, 170, 2, 17, 0, 0, 0, 7, 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