Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 968053c89d34f04ba36e5b1c4ae240136410256b9f4daa646d800de3fdaa1773

Tx prefix hash: 7c7c20f48fcd344132129db04ee9edfab791c1a4638435a08feec5bbd191f4a1
Tx public key: 01c5790b9736151107803e061b063a8178603c90ffb2fd4d7784d42f1fe5e631
Timestamp: 1722094623 Timestamp [UCT]: 2024-07-27 15:37:03 Age [y:d:h:m:s]: 00:248:17:30:02
Block: 1074919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177665 RingCT/type: yes/0
Extra: 0101c5790b9736151107803e061b063a8178603c90ffb2fd4d7784d42f1fe5e631021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c997c1fe0e424a7203241b7c07d53e90836c1d7cadc0aa41ad6bbf06b0982292 0.600000000000 1547438 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": 1074929, "vin": [ { "gen": { "height": 1074919 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c997c1fe0e424a7203241b7c07d53e90836c1d7cadc0aa41ad6bbf06b0982292" } } ], "extra": [ 1, 1, 197, 121, 11, 151, 54, 21, 17, 7, 128, 62, 6, 27, 6, 58, 129, 120, 96, 60, 144, 255, 178, 253, 77, 119, 132, 212, 47, 31, 229, 230, 49, 2, 17, 0, 0, 0, 3, 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