Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7b975900cfd31c5baee11970612cef3618d6fc0350308e52807f83b181ac361

Tx prefix hash: bcd3b682368d147c5b1d75dde9b664bea03a973e275761f77fed70aec32607d3
Tx public key: efe3d80a6c35271ef1bb33e96cef4f1703e48d1142e53b08540cdd318d0514c5
Timestamp: 1721607044 Timestamp [UCT]: 2024-07-22 00:10:44 Age [y:d:h:m:s]: 00:218:09:28:14
Block: 1070863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155981 RingCT/type: yes/0
Extra: 01efe3d80a6c35271ef1bb33e96cef4f1703e48d1142e53b08540cdd318d0514c5021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9402dc75d2b9c71fdee7f3e784e337ab9778d93c6b191120e2cbc2150274a9a 0.600000000000 1542874 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": 1070873, "vin": [ { "gen": { "height": 1070863 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9402dc75d2b9c71fdee7f3e784e337ab9778d93c6b191120e2cbc2150274a9a" } } ], "extra": [ 1, 239, 227, 216, 10, 108, 53, 39, 30, 241, 187, 51, 233, 108, 239, 79, 23, 3, 228, 141, 17, 66, 229, 59, 8, 84, 12, 221, 49, 141, 5, 20, 197, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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