Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 593b437914341cf1bf26b3a6f6f3905bfef95987ef47e81d8749da33edacd1d7

Tx prefix hash: 0c4ab3f9a391873229f729e46348da88a925ef01731d327ef72152dc5ed176fc
Tx public key: 756d0d726001b050ae4c236af8abcf60131e4526a92a1555158b3b9222ed45e5
Timestamp: 1581422999 Timestamp [UCT]: 2020-02-11 12:09:59 Age [y:d:h:m:s]: 04:332:15:26:38
Block: 62591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1130022 RingCT/type: yes/0
Extra: 01756d0d726001b050ae4c236af8abcf60131e4526a92a1555158b3b9222ed45e5021100000002d81c26c0000000000000000000

1 output(s) for total of 380.731100846000 dcy

stealth address amount amount idx
00: 7062e3b06b9eff6fb5bdcecb0220a366e763084c05995e1e8c0fbf1f42c0eb2c 380.731100846000 115547 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": 62601, "vin": [ { "gen": { "height": 62591 } } ], "vout": [ { "amount": 380731100846, "target": { "key": "7062e3b06b9eff6fb5bdcecb0220a366e763084c05995e1e8c0fbf1f42c0eb2c" } } ], "extra": [ 1, 117, 109, 13, 114, 96, 1, 176, 80, 174, 76, 35, 106, 248, 171, 207, 96, 19, 30, 69, 38, 169, 42, 21, 85, 21, 139, 59, 146, 34, 237, 69, 229, 2, 17, 0, 0, 0, 2, 216, 28, 38, 192, 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