Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6055f800d83a82b49d058cdab3d106f7d6638fdec6f0da00e928f5126918f48

Tx prefix hash: 647ca4d73d75f3163216751e106263086b5d7e91ea3d1ab67d2965a5552f3c35
Tx public key: b2f54f83ca777a5d4795ade085bca945082c4a5279ac89ed8e2660bc794bb101
Timestamp: 1582129829 Timestamp [UCT]: 2020-02-19 16:30:29 Age [y:d:h:m:s]: 04:260:12:15:42
Block: 68316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1078532 RingCT/type: yes/0
Extra: 01b2f54f83ca777a5d4795ade085bca945082c4a5279ac89ed8e2660bc794bb101021100000009d81c26c0000000000000000000

1 output(s) for total of 364.453007843000 dcy

stealth address amount amount idx
00: c87b31c3390b965fd936804f4d8921458ff2f80111650c590fa7a5d6afdf0e0b 364.453007843000 125868 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": 68326, "vin": [ { "gen": { "height": 68316 } } ], "vout": [ { "amount": 364453007843, "target": { "key": "c87b31c3390b965fd936804f4d8921458ff2f80111650c590fa7a5d6afdf0e0b" } } ], "extra": [ 1, 178, 245, 79, 131, 202, 119, 122, 93, 71, 149, 173, 224, 133, 188, 169, 69, 8, 44, 74, 82, 121, 172, 137, 237, 142, 38, 96, 188, 121, 75, 177, 1, 2, 17, 0, 0, 0, 9, 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