Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 378a6bf7c2325d059880b2f2edda24bf30f4ebfcc2d8066f5471813d251f7b40

Tx prefix hash: d38c34b8b198eb361374996d50f03b312aca7b71ace155f0af3cc5130672751d
Tx public key: 1bb383421eb72f0621df96628941e819592e85dcf233a11c1b897fd7bca5f415
Timestamp: 1722747974 Timestamp [UCT]: 2024-08-04 05:06:14 Age [y:d:h:m:s]: 00:248:06:34:22
Block: 1080338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177345 RingCT/type: yes/0
Extra: 011bb383421eb72f0621df96628941e819592e85dcf233a11c1b897fd7bca5f415021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9e63e2bc82d4f2c19392f2e6076618ae7b3a97344dc8aee4f7f2cd1d8e79a22 0.600000000000 1553649 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": 1080348, "vin": [ { "gen": { "height": 1080338 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9e63e2bc82d4f2c19392f2e6076618ae7b3a97344dc8aee4f7f2cd1d8e79a22" } } ], "extra": [ 1, 27, 179, 131, 66, 30, 183, 47, 6, 33, 223, 150, 98, 137, 65, 232, 25, 89, 46, 133, 220, 242, 51, 161, 28, 27, 137, 127, 215, 188, 165, 244, 21, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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