Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d38ed63b7a44d887e51b6fe33b540bc80cfbbb6c1a90ddd44301d6a898047eea

Tx prefix hash: 7a1de2084af9a35fdc3dad7a1e1128e0d566597e1cb5bfc4713b36ad4eaff88d
Tx public key: cfc71e03bd0e6260587344bc2516a1f1491a59832c379a32924cd5a3daece509
Timestamp: 1695600350 Timestamp [UCT]: 2023-09-25 00:05:50 Age [y:d:h:m:s]: 01:186:07:51:42
Block: 855466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394226 RingCT/type: yes/0
Extra: 01cfc71e03bd0e6260587344bc2516a1f1491a59832c379a32924cd5a3daece50902110000000c33af99f4000000000000000000

1 output(s) for total of 0.898433774000 dcy

stealth address amount amount idx
00: f595fa797e5ae03a5ffac2e052e35321e1a028ed1894eb5741dfab3a0eff2609 0.898433774000 1309488 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": 855476, "vin": [ { "gen": { "height": 855466 } } ], "vout": [ { "amount": 898433774, "target": { "key": "f595fa797e5ae03a5ffac2e052e35321e1a028ed1894eb5741dfab3a0eff2609" } } ], "extra": [ 1, 207, 199, 30, 3, 189, 14, 98, 96, 88, 115, 68, 188, 37, 22, 161, 241, 73, 26, 89, 131, 44, 55, 154, 50, 146, 76, 213, 163, 218, 236, 229, 9, 2, 17, 0, 0, 0, 12, 51, 175, 153, 244, 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