Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec137aa64170c9f35fbe64259f006c6a26522ca4492a04aa1447d2bb51d8dc2b

Tx prefix hash: c9eeff8a738154419e3591c054868c9c83d513cb29edc4490b400f2650ff8899
Tx public key: 39321b424b700868b0d368913c723d7ebe6df88a7996b68a38169131867fbaef
Timestamp: 1583528336 Timestamp [UCT]: 2020-03-06 20:58:56 Age [y:d:h:m:s]: 05:088:12:57:43
Block: 77563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1218699 RingCT/type: yes/0
Extra: 0139321b424b700868b0d368913c723d7ebe6df88a7996b68a38169131867fbaef02110000000cd81c26c0000000000000000000

1 output(s) for total of 339.627131123000 dcy

stealth address amount amount idx
00: bec8e64c13fd2d8d393d4b0d54cfc7723e7dcb1a139cd1d82b42536b2735f9a3 339.627131123000 142704 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": 77573, "vin": [ { "gen": { "height": 77563 } } ], "vout": [ { "amount": 339627131123, "target": { "key": "bec8e64c13fd2d8d393d4b0d54cfc7723e7dcb1a139cd1d82b42536b2735f9a3" } } ], "extra": [ 1, 57, 50, 27, 66, 75, 112, 8, 104, 176, 211, 104, 145, 60, 114, 61, 126, 190, 109, 248, 138, 121, 150, 182, 138, 56, 22, 145, 49, 134, 127, 186, 239, 2, 17, 0, 0, 0, 12, 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