Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b03b0464952b27602f0c79021bc53af32d0df807d3d809f778cf8cdb61094a51

Tx prefix hash: 04ba5c746bbdd1308b44e3199cdc846610c7018d04308002c1e2119b70901cd2
Tx public key: a66f26e0f071ec072a1bba13c5e49b29f2db2141a9e50ac9fc47a715c2280480
Timestamp: 1717561292 Timestamp [UCT]: 2024-06-05 04:21:32 Age [y:d:h:m:s]: 00:232:09:02:12
Block: 1037344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166249 RingCT/type: yes/0
Extra: 01a66f26e0f071ec072a1bba13c5e49b29f2db2141a9e50ac9fc47a715c22804800211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35c884d4f6c77d23218dd6c9d3506308ad33c41ad4f7c6ce5bf591feb9b3c134 0.600000000000 1505875 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": 1037354, "vin": [ { "gen": { "height": 1037344 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35c884d4f6c77d23218dd6c9d3506308ad33c41ad4f7c6ce5bf591feb9b3c134" } } ], "extra": [ 1, 166, 111, 38, 224, 240, 113, 236, 7, 42, 27, 186, 19, 197, 228, 155, 41, 242, 219, 33, 65, 169, 229, 10, 201, 252, 71, 167, 21, 194, 40, 4, 128, 2, 17, 0, 0, 0, 5, 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