Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33ce820fd8585aaaff2fc11f2a3e32f5762eff4970e817734c18c97773fa74fc

Tx prefix hash: cdf8b80edff013d586edcc2ad60bb246a67a7ac58cb84222da598a12c7ba9efb
Tx public key: f5d3b3b0df4baad88436456d86782d031bf87db2091f0e70d9ff7973e1f2fc4b
Timestamp: 1718150300 Timestamp [UCT]: 2024-06-11 23:58:20 Age [y:d:h:m:s]: 00:172:22:49:35
Block: 1042225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123783 RingCT/type: yes/0
Extra: 01f5d3b3b0df4baad88436456d86782d031bf87db2091f0e70d9ff7973e1f2fc4b02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5117b7b8d7dbe44b7d9bf1c329624a68f77f06ca47c772ad922e2ba5c0e2b279 0.600000000000 1511094 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": 1042235, "vin": [ { "gen": { "height": 1042225 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5117b7b8d7dbe44b7d9bf1c329624a68f77f06ca47c772ad922e2ba5c0e2b279" } } ], "extra": [ 1, 245, 211, 179, 176, 223, 75, 170, 216, 132, 54, 69, 109, 134, 120, 45, 3, 27, 248, 125, 178, 9, 31, 14, 112, 217, 255, 121, 115, 225, 242, 252, 75, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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