Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ac422260d3e6024e8403fb785fc8cea14ac7eaaede3122c98a7c0853c3f929e

Tx prefix hash: 1fdfdc73511c6312718d230a7669007ffdfc76983c8335321637b562e3073ef0
Tx public key: 5673e5978b2c3bed7f5e5e580c8aaacf49a1a11b019dd9efbae3dc412ff20b8b
Timestamp: 1661620031 Timestamp [UCT]: 2022-08-27 17:07:11 Age [y:d:h:m:s]: 02:292:18:14:38
Block: 575069 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 730432 RingCT/type: yes/0
Extra: 015673e5978b2c3bed7f5e5e580c8aaacf49a1a11b019dd9efbae3dc412ff20b8b02110000000375e3f0e9000000000000000000

1 output(s) for total of 7.630583973000 dcy

stealth address amount amount idx
00: 801ab804039a0fb00d46d06de54314cb4535a37a3be2e0f274c4edfad7cb083d 7.630583973000 1008403 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": 575079, "vin": [ { "gen": { "height": 575069 } } ], "vout": [ { "amount": 7630583973, "target": { "key": "801ab804039a0fb00d46d06de54314cb4535a37a3be2e0f274c4edfad7cb083d" } } ], "extra": [ 1, 86, 115, 229, 151, 139, 44, 59, 237, 127, 94, 94, 88, 12, 138, 170, 207, 73, 161, 161, 27, 1, 157, 217, 239, 186, 227, 220, 65, 47, 242, 11, 139, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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