Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3850e06407b999f21e8a0307c6e9d0d3ae0284ecdcfba44ddf3008f2bdd520d7

Tx prefix hash: 269db7aea7b419b2145f7bdc4e2d56356e213ce017edd59c330ad1c8f833a77b
Tx public key: 9a08273558e30eae167d99934bd9724d835986cad062b5b3f93e0f68244db371
Timestamp: 1712785453 Timestamp [UCT]: 2024-04-10 21:44:13 Age [y:d:h:m:s]: 01:017:02:28:10
Block: 997720 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273213 RingCT/type: yes/0
Extra: 019a08273558e30eae167d99934bd9724d835986cad062b5b3f93e0f68244db3710211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2fd4c17475dd7a8e40ef5a1587fa255b155a6ec2dff0d443be5b384ea8b9a1c9 0.600000000000 1458154 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": 997730, "vin": [ { "gen": { "height": 997720 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2fd4c17475dd7a8e40ef5a1587fa255b155a6ec2dff0d443be5b384ea8b9a1c9" } } ], "extra": [ 1, 154, 8, 39, 53, 88, 227, 14, 174, 22, 125, 153, 147, 75, 217, 114, 77, 131, 89, 134, 202, 208, 98, 181, 179, 249, 62, 15, 104, 36, 77, 179, 113, 2, 17, 0, 0, 0, 1, 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