Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fff45ce7078e41b4febbf7ed2b09e80e93adc0b631a87b62279223fe1c9d5ba

Tx prefix hash: 58a12d13a295564bc67a7e3a207dee0b884402e66606840cc8e2bd0e2325b447
Tx public key: 413c6c57ec4cbbf1104257a6bd4fef99573e0f941ab0915853f95f5eceee1054
Timestamp: 1721997824 Timestamp [UCT]: 2024-07-26 12:43:44 Age [y:d:h:m:s]: 01:166:16:06:03
Block: 1074120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377691 RingCT/type: yes/0
Extra: 01413c6c57ec4cbbf1104257a6bd4fef99573e0f941ab0915853f95f5eceee1054021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5b07b3a41e5d8a593301b81c516ee9c09df6a120baf5137208df00967abd077 0.600000000000 1546633 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": 1074130, "vin": [ { "gen": { "height": 1074120 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5b07b3a41e5d8a593301b81c516ee9c09df6a120baf5137208df00967abd077" } } ], "extra": [ 1, 65, 60, 108, 87, 236, 76, 187, 241, 16, 66, 87, 166, 189, 79, 239, 153, 87, 62, 15, 148, 26, 176, 145, 88, 83, 249, 95, 94, 206, 238, 16, 84, 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