Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13c53dc895d62857c9611ea20465eb41ea27b90bdb6b20ee4640f50de4eeae1e

Tx prefix hash: 31502a459b6f66351bdc1cb8a95517e1a518729499731d1043ca8bb17e87c463
Tx public key: 713dcc726d884921e8fa53495a7e29c5235c736f6f8928affb9a8b80e41bce4e
Timestamp: 1711688873 Timestamp [UCT]: 2024-03-29 05:07:53 Age [y:d:h:m:s]: 00:287:13:45:53
Block: 988666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205834 RingCT/type: yes/0
Extra: 01713dcc726d884921e8fa53495a7e29c5235c736f6f8928affb9a8b80e41bce4e0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2840bc4aeff1e1ed4a7dd260fdc0367a4aadb2c8d1b6a78aecc416dec4e18bbd 0.600000000000 1448947 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": 988676, "vin": [ { "gen": { "height": 988666 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2840bc4aeff1e1ed4a7dd260fdc0367a4aadb2c8d1b6a78aecc416dec4e18bbd" } } ], "extra": [ 1, 113, 61, 204, 114, 109, 136, 73, 33, 232, 250, 83, 73, 90, 126, 41, 197, 35, 92, 115, 111, 111, 137, 40, 175, 251, 154, 139, 128, 228, 27, 206, 78, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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