Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e049dab8b65586570a8602ffac6d5f561716931a7fc5ea4f6ae441b5550201b

Tx prefix hash: 02c35d058755b9b74d64dfccd799093c62689eb8047123ca9ce5aa5dea3f6f67
Tx public key: f10074c567293c1b01a1749461e5ee1bec1caa6a9103469eb4ba7ba03942e12e
Timestamp: 1699069319 Timestamp [UCT]: 2023-11-04 03:41:59 Age [y:d:h:m:s]: 01:196:23:47:26
Block: 884239 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401796 RingCT/type: yes/0
Extra: 01f10074c567293c1b01a1749461e5ee1bec1caa6a9103469eb4ba7ba03942e12e02110000000233af99f4000000000000000000

1 output(s) for total of 0.721355146000 dcy

stealth address amount amount idx
00: c83c23b80a3d8580ec5f112521c1dfdbeab4afab9b7ee19a140d0298ee29d0d4 0.721355146000 1339976 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": 884249, "vin": [ { "gen": { "height": 884239 } } ], "vout": [ { "amount": 721355146, "target": { "key": "c83c23b80a3d8580ec5f112521c1dfdbeab4afab9b7ee19a140d0298ee29d0d4" } } ], "extra": [ 1, 241, 0, 116, 197, 103, 41, 60, 27, 1, 161, 116, 148, 97, 229, 238, 27, 236, 28, 170, 106, 145, 3, 70, 158, 180, 186, 123, 160, 57, 66, 225, 46, 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