Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15dba0d143dd711d6c4eca99c906a96747de8e0979dc5820c03f698d88c72be2

Tx prefix hash: 580f9ed26f98933f997a4940feeb5116927b918104f181fe0db29f0f85fcde2b
Tx public key: d9e357dd87b3c1f98edef60f7078370a2240ccaeaf11aa407fcb6dd80c808d19
Timestamp: 1588734323 Timestamp [UCT]: 2020-05-06 03:05:23 Age [y:d:h:m:s]: 04:241:06:37:57
Block: 98727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1089059 RingCT/type: yes/0
Extra: 01d9e357dd87b3c1f98edef60f7078370a2240ccaeaf11aa407fcb6dd80c808d1902110000000160e3cc90000000000000000000

1 output(s) for total of 288.986283124000 dcy

stealth address amount amount idx
00: 180a12585aa7d265c1a1cfd84be4ba8ce44f3e1c1cdb716cdea3633e8d99810c 288.986283124000 174465 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": 98737, "vin": [ { "gen": { "height": 98727 } } ], "vout": [ { "amount": 288986283124, "target": { "key": "180a12585aa7d265c1a1cfd84be4ba8ce44f3e1c1cdb716cdea3633e8d99810c" } } ], "extra": [ 1, 217, 227, 87, 221, 135, 179, 193, 249, 142, 222, 246, 15, 112, 120, 55, 10, 34, 64, 204, 174, 175, 17, 170, 64, 127, 203, 109, 216, 12, 128, 141, 25, 2, 17, 0, 0, 0, 1, 96, 227, 204, 144, 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