Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5aa74a669fefd08457873e033d2a7dffd97f764b7e74cbf8e30af4d3f5c4ecc4

Tx prefix hash: f0459c0f4c989e0669c4b28f7907ce882e34aa9aa2e6557023586620ebd64d24
Tx public key: 949fc4169cfa9a269f44fbbf55056bb87b4b921d32e0dcad3f59877a1b31eaa7
Timestamp: 1728818773 Timestamp [UCT]: 2024-10-13 11:26:13 Age [y:d:h:m:s]: 00:046:01:04:39
Block: 1130674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32881 RingCT/type: yes/0
Extra: 01949fc4169cfa9a269f44fbbf55056bb87b4b921d32e0dcad3f59877a1b31eaa7021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c0ce69b2fee3a8b2f6a1d28d032495747e597855259f66dac2e6c42bf7fc3b3 0.600000000000 1613551 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": 1130684, "vin": [ { "gen": { "height": 1130674 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c0ce69b2fee3a8b2f6a1d28d032495747e597855259f66dac2e6c42bf7fc3b3" } } ], "extra": [ 1, 148, 159, 196, 22, 156, 250, 154, 38, 159, 68, 251, 191, 85, 5, 107, 184, 123, 75, 146, 29, 50, 224, 220, 173, 63, 89, 135, 122, 27, 49, 234, 167, 2, 17, 0, 0, 0, 5, 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