Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf80761a2488cc6eaf512aed6dcdb809a4d59f8173052b933089518ddc7d981b

Tx prefix hash: dd40f1fb782cfce83f5a3f46992373232eec5db3da79917a4d03cf41ec8aa55d
Tx public key: 5044ed709f28f4b1cb55fd05383a5614f298a8cc8c45b8f194e4582ef84a794b
Timestamp: 1728398995 Timestamp [UCT]: 2024-10-08 14:49:55 Age [y:d:h:m:s]: 00:164:21:35:54
Block: 1127189 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117640 RingCT/type: yes/0
Extra: 015044ed709f28f4b1cb55fd05383a5614f298a8cc8c45b8f194e4582ef84a794b021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30c4f396fe70a7c3aadb653a6fc341555d49ca1fa28351a6516df6bb37f199da 0.600000000000 1609990 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": 1127199, "vin": [ { "gen": { "height": 1127189 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30c4f396fe70a7c3aadb653a6fc341555d49ca1fa28351a6516df6bb37f199da" } } ], "extra": [ 1, 80, 68, 237, 112, 159, 40, 244, 177, 203, 85, 253, 5, 56, 58, 86, 20, 242, 152, 168, 204, 140, 69, 184, 241, 148, 228, 88, 46, 248, 74, 121, 75, 2, 17, 0, 0, 0, 2, 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