Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fef31d40c463d6d4ad0a256d992f2c732499a4f35d74705fea7d61e03119cdb9

Tx prefix hash: 3877d51603760dde87b41129b0982513f7ef45b7aec55fd4db2107bcb94f899d
Tx public key: 17c085cee4073f668587f4dbaf43a6f0a1eae4d64279aa3ef4e56ef2ea965027
Timestamp: 1709881966 Timestamp [UCT]: 2024-03-08 07:12:46 Age [y:d:h:m:s]: 01:243:08:46:23
Block: 973682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 432625 RingCT/type: yes/0
Extra: 0117c085cee4073f668587f4dbaf43a6f0a1eae4d64279aa3ef4e56ef2ea9650270211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3833f469352cf69591c8c4c040798cb4dd76f09d20f72544b37d3891806d1728 0.600000000000 1433617 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": 973692, "vin": [ { "gen": { "height": 973682 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3833f469352cf69591c8c4c040798cb4dd76f09d20f72544b37d3891806d1728" } } ], "extra": [ 1, 23, 192, 133, 206, 228, 7, 63, 102, 133, 135, 244, 219, 175, 67, 166, 240, 161, 234, 228, 214, 66, 121, 170, 62, 244, 229, 110, 242, 234, 150, 80, 39, 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