Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f8eb3231e28a64469fcbf1c2d430890fc194de70106fa11d2b4288136436c28

Tx prefix hash: b518730423a2d9917d6dc06eccc1bb04071bbfe72153ac9f04699335b612352f
Tx public key: 204d4194a5fc016216d2a378c006f2d4236b466c00a911ff396a40fb1a4b1641
Timestamp: 1657286201 Timestamp [UCT]: 2022-07-08 13:16:41 Age [y:d:h:m:s]: 02:257:11:47:15
Block: 539338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 705151 RingCT/type: yes/0
Extra: 01204d4194a5fc016216d2a378c006f2d4236b466c00a911ff396a40fb1a4b1641021100000002bf7ee4e7000000000000000000

1 output(s) for total of 10.021886133000 dcy

stealth address amount amount idx
00: 41a9c0ee4fb37b453f6b5e2da07d64b9d0536f187cdeea6c58363637c1c96b39 10.021886133000 969429 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": 539348, "vin": [ { "gen": { "height": 539338 } } ], "vout": [ { "amount": 10021886133, "target": { "key": "41a9c0ee4fb37b453f6b5e2da07d64b9d0536f187cdeea6c58363637c1c96b39" } } ], "extra": [ 1, 32, 77, 65, 148, 165, 252, 1, 98, 22, 210, 163, 120, 192, 6, 242, 212, 35, 107, 70, 108, 0, 169, 17, 255, 57, 106, 64, 251, 26, 75, 22, 65, 2, 17, 0, 0, 0, 2, 191, 126, 228, 231, 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