Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f038d0ce48101dfb4c554ac1ee7ecffc348fbfdec51c80704a011d7819b72131

Tx prefix hash: ddc7ce9dd2468bf8aff0ad099239809d45035dbe5355d597f2c6358220f1d3e1
Tx public key: 2bc8927b7a3c0259b382b5028bbfb4d081ac58931115068a6e79c852cef3a5c7
Timestamp: 1716908802 Timestamp [UCT]: 2024-05-28 15:06:42 Age [y:d:h:m:s]: 00:270:07:48:41
Block: 1031943 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193151 RingCT/type: yes/0
Extra: 012bc8927b7a3c0259b382b5028bbfb4d081ac58931115068a6e79c852cef3a5c70211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49f3a051b6f97d4048263af3944cd14c4db27c4d04b4b9c65bf93ed44b24bf94 0.600000000000 1500392 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": 1031953, "vin": [ { "gen": { "height": 1031943 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49f3a051b6f97d4048263af3944cd14c4db27c4d04b4b9c65bf93ed44b24bf94" } } ], "extra": [ 1, 43, 200, 146, 123, 122, 60, 2, 89, 179, 130, 181, 2, 139, 191, 180, 208, 129, 172, 88, 147, 17, 21, 6, 138, 110, 121, 200, 82, 206, 243, 165, 199, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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