Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8bb89a1e9fd6756d033e1cf13afacb17b470d93b2be9dfc776b45b827c462001

Tx prefix hash: f24d6eff5fd5f90e64fc2866092672e2902e50d33c3b408ca16091532f23a4d9
Tx public key: d56620574f02bf5a20233c965df032217bd503f7cd0ef0c58d1b44ec477084a8
Timestamp: 1707705431 Timestamp [UCT]: 2024-02-12 02:37:11 Age [y:d:h:m:s]: 01:126:12:51:17
Block: 955617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351423 RingCT/type: yes/0
Extra: 01d56620574f02bf5a20233c965df032217bd503f7cd0ef0c58d1b44ec477084a802110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 601f805303f5198c8d09674d8f05816ae5535e25d557887c694e10f45b90ab2f 0.600000000000 1414915 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": 955627, "vin": [ { "gen": { "height": 955617 } } ], "vout": [ { "amount": 600000000, "target": { "key": "601f805303f5198c8d09674d8f05816ae5535e25d557887c694e10f45b90ab2f" } } ], "extra": [ 1, 213, 102, 32, 87, 79, 2, 191, 90, 32, 35, 60, 150, 93, 240, 50, 33, 123, 213, 3, 247, 205, 14, 240, 197, 141, 27, 68, 236, 71, 112, 132, 168, 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