Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27fe8a804b29cd4941eb7ab036701cc791b5b052bb57ca306ba559212d0e7ea9

Tx prefix hash: ed94cb37bc7f0423657897ac80f910c3da26e71e6795335333386023172ccaff
Tx public key: d3e2f47dbcb897230ae074a227035da06a4a33ada9ea2513b18563388e4dcf48
Timestamp: 1724406060 Timestamp [UCT]: 2024-08-23 09:41:00 Age [y:d:h:m:s]: 00:246:01:20:12
Block: 1094105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175717 RingCT/type: yes/0
Extra: 01d3e2f47dbcb897230ae074a227035da06a4a33ada9ea2513b18563388e4dcf48021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 049cf022e725bad86c0c7b1b8d6ea38b825005a9f63d6d582a89789de5d5f982 0.600000000000 1569180 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": 1094115, "vin": [ { "gen": { "height": 1094105 } } ], "vout": [ { "amount": 600000000, "target": { "key": "049cf022e725bad86c0c7b1b8d6ea38b825005a9f63d6d582a89789de5d5f982" } } ], "extra": [ 1, 211, 226, 244, 125, 188, 184, 151, 35, 10, 224, 116, 162, 39, 3, 93, 160, 106, 74, 51, 173, 169, 234, 37, 19, 177, 133, 99, 56, 142, 77, 207, 72, 2, 17, 0, 0, 0, 6, 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