Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de561fcc382fbca2626473275b5d085290920d010fae654bcd304dc1a7c0fd04

Tx prefix hash: b461e1cce028ea4f225b91046d56b1fda1999e80a77673c805a6c9df07dccb0e
Tx public key: 58a70b3babe9c8de401e7202590c39f8601caf83de8823390c80d9734132eab1
Timestamp: 1694266210 Timestamp [UCT]: 2023-09-09 13:30:10 Age [y:d:h:m:s]: 01:206:23:38:51
Block: 844390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 409035 RingCT/type: yes/0
Extra: 0158a70b3babe9c8de401e7202590c39f8601caf83de8823390c80d9734132eab102110000000b4b8f5122000000000000000000

1 output(s) for total of 0.977654654000 dcy

stealth address amount amount idx
00: f324722a3adff5c80c5b4a1deb122f1a59ae994c88cf52e5c59f74c986df3d17 0.977654654000 1297696 of 0

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": 844400, "vin": [ { "gen": { "height": 844390 } } ], "vout": [ { "amount": 977654654, "target": { "key": "f324722a3adff5c80c5b4a1deb122f1a59ae994c88cf52e5c59f74c986df3d17" } } ], "extra": [ 1, 88, 167, 11, 59, 171, 233, 200, 222, 64, 30, 114, 2, 89, 12, 57, 248, 96, 28, 175, 131, 222, 136, 35, 57, 12, 128, 217, 115, 65, 50, 234, 177, 2, 17, 0, 0, 0, 11, 75, 143, 81, 34, 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