Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5aa0784e5f644015a41cc839ce667b09c095ae16096ba04b7480e7d746b4ce8e

Tx prefix hash: d35f18b17c2b3f6816c9dddb10436f42c03deb5a8ddb3907e0f0e66810c4a77b
Tx public key: 7188372c93fc8a2ca6e88264f0218a2729a478d8d03a98b60b7c651238f2599d
Timestamp: 1637587172 Timestamp [UCT]: 2021-11-22 13:19:32 Age [y:d:h:m:s]: 03:343:17:42:52
Block: 379697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1022072 RingCT/type: yes/0
Extra: 017188372c93fc8a2ca6e88264f0218a2729a478d8d03a98b60b7c651238f2599d021100000009379224c2000000000000000000

1 output(s) for total of 33.877129201000 dcy

stealth address amount amount idx
00: 200ab73dcbf7cdfe88df15ee6772bd109fc3bd770fe7daaae4940ddb469b840e 33.877129201000 767435 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": 379707, "vin": [ { "gen": { "height": 379697 } } ], "vout": [ { "amount": 33877129201, "target": { "key": "200ab73dcbf7cdfe88df15ee6772bd109fc3bd770fe7daaae4940ddb469b840e" } } ], "extra": [ 1, 113, 136, 55, 44, 147, 252, 138, 44, 166, 232, 130, 100, 240, 33, 138, 39, 41, 164, 120, 216, 208, 58, 152, 182, 11, 124, 101, 18, 56, 242, 89, 157, 2, 17, 0, 0, 0, 9, 55, 146, 36, 194, 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