Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3266f51f71dddaf1376b6225a1b10c47c5f8940cc30d15d275cb3ea4722e056

Tx prefix hash: 776ed4efe6930fc923e55c0aae60035b95eb5dc5c42d8bd41fb624eb8ab77833
Tx public key: d0e6ca1f7cc9439abee72aaccfc9185e2747b5ecc1cf0ed9d71267d67570fcbd
Timestamp: 1722508248 Timestamp [UCT]: 2024-08-01 10:30:48 Age [y:d:h:m:s]: 01:100:01:23:46
Block: 1078343 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330005 RingCT/type: yes/0
Extra: 01d0e6ca1f7cc9439abee72aaccfc9185e2747b5ecc1cf0ed9d71267d67570fcbd021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bde0f6bc0c0a131344acaf37558cb58437c3a6400186d3ffffa62e83a1cc4dd2 0.600000000000 1550920 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": 1078353, "vin": [ { "gen": { "height": 1078343 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bde0f6bc0c0a131344acaf37558cb58437c3a6400186d3ffffa62e83a1cc4dd2" } } ], "extra": [ 1, 208, 230, 202, 31, 124, 201, 67, 154, 190, 231, 42, 172, 207, 201, 24, 94, 39, 71, 181, 236, 193, 207, 14, 217, 215, 18, 103, 214, 117, 112, 252, 189, 2, 17, 0, 0, 0, 8, 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