Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe09a3639de75e00ef2fa22c7ea365b658938ae0e884e44a6634dc23a07111d9

Tx prefix hash: 685c1c8b02c9c630f55a970068d509543e4c38d0c2ca97f9746a50717bd1a57d
Tx public key: 06f565a2310533f6d92f5b769b31b9c06cef8c800b4e5aaa044fa970dc48d84d
Timestamp: 1737822220 Timestamp [UCT]: 2025-01-25 16:23:40 Age [y:d:h:m:s]: 00:048:08:21:47
Block: 1205119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34368 RingCT/type: yes/0
Extra: 0106f565a2310533f6d92f5b769b31b9c06cef8c800b4e5aaa044fa970dc48d84d021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 530f3e6387e4da05260fad0b904fd99f9cb31faeab52307001430ca34b1513a1 0.600000000000 1691816 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": 1205129, "vin": [ { "gen": { "height": 1205119 } } ], "vout": [ { "amount": 600000000, "target": { "key": "530f3e6387e4da05260fad0b904fd99f9cb31faeab52307001430ca34b1513a1" } } ], "extra": [ 1, 6, 245, 101, 162, 49, 5, 51, 246, 217, 47, 91, 118, 155, 49, 185, 192, 108, 239, 140, 128, 11, 78, 90, 170, 4, 79, 169, 112, 220, 72, 216, 77, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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