Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38b6c2144ed6968ad28375a93c0a8ee6c2975ea727e425997ecef00c569f56ee

Tx prefix hash: 03d198ae5578ba9972874bbfd85d8a91d22f92ad2a56d3bdf2b6fd1b12a4b1e4
Tx public key: 3c78ab43520396e5033a6dfc5f1fd8150161949670798bd84f03bd92eaa28caa
Timestamp: 1699016510 Timestamp [UCT]: 2023-11-03 13:01:50 Age [y:d:h:m:s]: 02:017:01:10:44
Block: 883807 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 531764 RingCT/type: yes/0
Extra: 013c78ab43520396e5033a6dfc5f1fd8150161949670798bd84f03bd92eaa28caa02110000000433af99f4000000000000000000

1 output(s) for total of 0.723736591000 dcy

stealth address amount amount idx
00: 0d62758c02b2e31b8f4497187bce1c3c4cb796c2e5ee1978c955c3b023330341 0.723736591000 1339522 of 0

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": 883817, "vin": [ { "gen": { "height": 883807 } } ], "vout": [ { "amount": 723736591, "target": { "key": "0d62758c02b2e31b8f4497187bce1c3c4cb796c2e5ee1978c955c3b023330341" } } ], "extra": [ 1, 60, 120, 171, 67, 82, 3, 150, 229, 3, 58, 109, 252, 95, 31, 216, 21, 1, 97, 148, 150, 112, 121, 139, 216, 79, 3, 189, 146, 234, 162, 140, 170, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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