Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3534bc5b49920f0482a8170dbf0972eafa07cdbe9123c8b5682b2c134d54ed7

Tx prefix hash: edbf8e6480a5376a28c9463f0f3e68552b5d4f92bae535c48f2fea6d79ed88cb
Tx public key: 8460c1b00d3149059bb56e77323291264f60cc2512a9c73a59d1b693d0cabbfa
Timestamp: 1717541332 Timestamp [UCT]: 2024-06-04 22:48:52 Age [y:d:h:m:s]: 00:299:19:36:08
Block: 1037183 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214257 RingCT/type: yes/0
Extra: 018460c1b00d3149059bb56e77323291264f60cc2512a9c73a59d1b693d0cabbfa02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1bc7c923c082a4f8e8a4839f6f877dcc0c315c54339629f89112ea772829caa7 0.600000000000 1505714 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": 1037193, "vin": [ { "gen": { "height": 1037183 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1bc7c923c082a4f8e8a4839f6f877dcc0c315c54339629f89112ea772829caa7" } } ], "extra": [ 1, 132, 96, 193, 176, 13, 49, 73, 5, 155, 181, 110, 119, 50, 50, 145, 38, 79, 96, 204, 37, 18, 169, 199, 58, 89, 209, 182, 147, 208, 202, 187, 250, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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