Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 697a44a77b6059dae86560696a9bde975dbf350f3dc57c7bf9709186180391b1

Tx prefix hash: 62a4f0d9ae6a3b1252900f2dca80b53d272b3dd1e18b2bf5d7c523ed7d90c995
Tx public key: 25b280b42828929c08c9e3fdcc11ec689f48ba3121c908be2a05009e40facca4
Timestamp: 1718335301 Timestamp [UCT]: 2024-06-14 03:21:41 Age [y:d:h:m:s]: 00:224:17:56:55
Block: 1043760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160775 RingCT/type: yes/0
Extra: 0125b280b42828929c08c9e3fdcc11ec689f48ba3121c908be2a05009e40facca40211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c83fdc3c559d4f4d1064a8518afb03b40e79487c041fd4bc3db836c3b6db32b 0.600000000000 1512919 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": 1043770, "vin": [ { "gen": { "height": 1043760 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c83fdc3c559d4f4d1064a8518afb03b40e79487c041fd4bc3db836c3b6db32b" } } ], "extra": [ 1, 37, 178, 128, 180, 40, 40, 146, 156, 8, 201, 227, 253, 204, 17, 236, 104, 159, 72, 186, 49, 33, 201, 8, 190, 42, 5, 0, 158, 64, 250, 204, 164, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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