Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb967cbe93aa6661ead7dbe9d598bdf763a00e4f13c2ca66453766219f2390de

Tx prefix hash: a6f115e590dfb00f3819527501501be6571909a777ac630391b0ec08a15c39bd
Tx public key: f2d0f0a3753254b2c7afe0e9f023fce27feaa94555f821a01a302e8ccc1c8148
Timestamp: 1706651646 Timestamp [UCT]: 2024-01-30 21:54:06 Age [y:d:h:m:s]: 01:288:10:56:24
Block: 946873 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 464967 RingCT/type: yes/0
Extra: 01f2d0f0a3753254b2c7afe0e9f023fce27feaa94555f821a01a302e8ccc1c81480211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e02dd5807b15517e2223aa2bc3bc9b0af6d719bf6ca1744f794b2dfe73ca607d 0.600000000000 1405215 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": 946883, "vin": [ { "gen": { "height": 946873 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e02dd5807b15517e2223aa2bc3bc9b0af6d719bf6ca1744f794b2dfe73ca607d" } } ], "extra": [ 1, 242, 208, 240, 163, 117, 50, 84, 178, 199, 175, 224, 233, 240, 35, 252, 226, 127, 234, 169, 69, 85, 248, 33, 160, 26, 48, 46, 140, 204, 28, 129, 72, 2, 17, 0, 0, 0, 6, 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