Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b31573622202325011ec105e27f479d6d8a81cd9c5c444dcd9f44c74124021ad

Tx prefix hash: 1e983a29b1216a5745271fa2959360a1a14fb2f2df17bd3990d34d0a45e7dc72
Tx public key: 7dd652180806099d71082f15a60fc41a2283ea0594dff3a17b92cb162b9d4fbf
Timestamp: 1723744670 Timestamp [UCT]: 2024-08-15 17:57:50 Age [y:d:h:m:s]: 00:252:03:27:52
Block: 1088598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180098 RingCT/type: yes/0
Extra: 017dd652180806099d71082f15a60fc41a2283ea0594dff3a17b92cb162b9d4fbf021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc2eec57d81a35c2a2609f1f085314a16b693f66098f003c63125c36e623e3d5 0.600000000000 1563215 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": 1088608, "vin": [ { "gen": { "height": 1088598 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc2eec57d81a35c2a2609f1f085314a16b693f66098f003c63125c36e623e3d5" } } ], "extra": [ 1, 125, 214, 82, 24, 8, 6, 9, 157, 113, 8, 47, 21, 166, 15, 196, 26, 34, 131, 234, 5, 148, 223, 243, 161, 123, 146, 203, 22, 43, 157, 79, 191, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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