Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf5e0628c5fec9dfd548e5f1dba1d266bfaadd7b2f63c4c1cda1006a0bd79375

Tx prefix hash: ca1cf459e7404954fa364a341213cfaaef387d2d2510a769056b312692fe25b4
Tx public key: 423e856e29f0046a3a8ff7b5f835135be8567422a4ea18292be48f566fee007b
Timestamp: 1630148583 Timestamp [UCT]: 2021-08-28 11:03:03 Age [y:d:h:m:s]: 03:159:22:55:23
Block: 322471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 888655 RingCT/type: yes/0
Extra: 01423e856e29f0046a3a8ff7b5f835135be8567422a4ea18292be48f566fee007b0211000000050441b428000000000000000000

1 output(s) for total of 52.422794783000 dcy

stealth address amount amount idx
00: b27e949a4d46edbf34f14a50def832ebb76d3ef9a0fe5cde025b98758410b810 52.422794783000 669133 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": 322481, "vin": [ { "gen": { "height": 322471 } } ], "vout": [ { "amount": 52422794783, "target": { "key": "b27e949a4d46edbf34f14a50def832ebb76d3ef9a0fe5cde025b98758410b810" } } ], "extra": [ 1, 66, 62, 133, 110, 41, 240, 4, 106, 58, 143, 247, 181, 248, 53, 19, 91, 232, 86, 116, 34, 164, 234, 24, 41, 43, 228, 143, 86, 111, 238, 0, 123, 2, 17, 0, 0, 0, 5, 4, 65, 180, 40, 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