Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 612eba48bda678d8ab5235356f841bdae443e7679efcf31d92b3f458792f977e

Tx prefix hash: b1bda54a020c5d95e6e32e1756cb1e97535bc0fdd4a263c467923d7afe1ee200
Tx public key: 7617c50fad702b8a4c74d57e0f3744a1e71c2593a3ee9bb92a3ef63c2a629659
Timestamp: 1699638102 Timestamp [UCT]: 2023-11-10 17:41:42 Age [y:d:h:m:s]: 01:152:05:19:58
Block: 888742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369984 RingCT/type: yes/0
Extra: 017617c50fad702b8a4c74d57e0f3744a1e71c2593a3ee9bb92a3ef63c2a62965902110000000233af99f4000000000000000000

1 output(s) for total of 0.696993647000 dcy

stealth address amount amount idx
00: 9ae4d95d4b43d6a65fa179386ce4aacd367843ae4d131c3b6d5a4d100cb5603a 0.696993647000 1344701 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": 888752, "vin": [ { "gen": { "height": 888742 } } ], "vout": [ { "amount": 696993647, "target": { "key": "9ae4d95d4b43d6a65fa179386ce4aacd367843ae4d131c3b6d5a4d100cb5603a" } } ], "extra": [ 1, 118, 23, 197, 15, 173, 112, 43, 138, 76, 116, 213, 126, 15, 55, 68, 161, 231, 28, 37, 147, 163, 238, 155, 185, 42, 62, 246, 60, 42, 98, 150, 89, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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