Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8557c1e9ddd58de13da2ec7967b2241b47be774ff5dba0709ed69a5e14e14af

Tx prefix hash: 279f1d958b401570cc1a02ff26d1e0de50e14f41dd011819f859be1cebfb380f
Tx public key: 49dadce8478889daa39e808c0c67f2f9e0d86a6aecdd3dae420c67580ddab862
Timestamp: 1698273381 Timestamp [UCT]: 2023-10-25 22:36:21 Age [y:d:h:m:s]: 01:089:02:29:56
Block: 877644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324868 RingCT/type: yes/0
Extra: 0149dadce8478889daa39e808c0c67f2f9e0d86a6aecdd3dae420c67580ddab862021100000008faf35c9c000000000000000000

1 output(s) for total of 0.758579526000 dcy

stealth address amount amount idx
00: a395d0023d7ef7429b307c336ce3963eea39669d2b1b45b7fd5d1ce8f78d51fc 0.758579526000 1333030 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": 877654, "vin": [ { "gen": { "height": 877644 } } ], "vout": [ { "amount": 758579526, "target": { "key": "a395d0023d7ef7429b307c336ce3963eea39669d2b1b45b7fd5d1ce8f78d51fc" } } ], "extra": [ 1, 73, 218, 220, 232, 71, 136, 137, 218, 163, 158, 128, 140, 12, 103, 242, 249, 224, 216, 106, 106, 236, 221, 61, 174, 66, 12, 103, 88, 13, 218, 184, 98, 2, 17, 0, 0, 0, 8, 250, 243, 92, 156, 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