Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5010f11846a82094b1ffb973aa51bef88d81cf25e653b497076f8800b546be5e

Tx prefix hash: 1fd26ba175420c0e6e7387774d50eeeac4881dcf142dfc26836781690a90b2d2
Tx public key: 3d0ea0e8d087f10dbd7168ed8500dc03b1be11d129f6a0c7f04e61aae7732108
Timestamp: 1717715043 Timestamp [UCT]: 2024-06-06 23:04:03 Age [y:d:h:m:s]: 00:146:20:27:32
Block: 1038613 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105106 RingCT/type: yes/0
Extra: 013d0ea0e8d087f10dbd7168ed8500dc03b1be11d129f6a0c7f04e61aae773210802110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f972826ebff6bfc96ffda542c96e2e81e0618ff8d32cc20482d495282a253a7 0.600000000000 1507174 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": 1038623, "vin": [ { "gen": { "height": 1038613 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f972826ebff6bfc96ffda542c96e2e81e0618ff8d32cc20482d495282a253a7" } } ], "extra": [ 1, 61, 14, 160, 232, 208, 135, 241, 13, 189, 113, 104, 237, 133, 0, 220, 3, 177, 190, 17, 209, 41, 246, 160, 199, 240, 78, 97, 170, 231, 115, 33, 8, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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